Curse

Beware · Feb 06, 2008, 01:55 AM // 01:55

While playing GW, my computer often shows a error box:

Out Of Memory
Array.cpp(88)

Not only that but I get different "Out Of Memory" errors as well.

I need to know what this problem is and how to fix it.

MrGuildBoi · Feb 06, 2008, 02:01 AM // 02:01

I get this too, usually when I continuously minimize :P

Beware · Feb 06, 2008, 02:19 AM // 02:19

I get this in the middle of playing GW. Its really annoying, specially when your in PvP. I need urgent help from an expert on this issue. PLZ

Narada · Feb 06, 2008, 10:08 AM // 10:08

Have either of you happened to look at your memory consumption at the time of crashing, or near it? The .cpp file extension references a C++ file, and as far as I know GW is coded in C++... It's possible that GW is closing in order to prevent buffer overflow after maxing out an array's buffer somewhere in its code, but that seems kind of self-defeating except from a security standpoint.

Anyways, first I'd try increasing your page file size and see if that does anything. What's it currently set at? Cleaning out your computer with AV and anti-*ware scans should probably free up a bit of memory too. If that doesn't work try closing some of the programs you have running that you don't need while gaming as well. If all else fails try reinstalling the GW client, but I'm skeptical about that being a solution. Feel free to post the results of anything you try out so we can possibly iron out the details.

Malice Black · Feb 06, 2008, 11:24 AM // 11:24

Set your paging file to 3GB.

Beware · Feb 06, 2008, 02:33 PM // 14:33

Do you need the specs of my comp?

Narada · Feb 06, 2008, 04:52 PM // 16:52

Quote:

Originally Posted by Beware

Do you need the specs of my comp?

Doubt it, but knowing how much memory you have installed in your computer might prove useful. Do you know how to set your page file size?

Beware · Feb 06, 2008, 07:19 PM // 19:19

I don't know how to change my page file, and what is it?

I have 1,24GB of RAM!

Narada · Feb 06, 2008, 08:35 PM // 20:35

Assuming you have WinXP:

1. Right-click My Computer and select Properties.
2. Click the Advanced tab.
3. In the Performance box, click the Settings button.
4. A window called Performance Options should come up. Click the Advanced tab.
5. In the Virtual Memory box, click the Change button.
6. A window called Virtual Memory should come up. There should be three different radio buttons labeled as Custom size, System managed size, and No paging file. Select the button labeled Custom size.
7. In the text box next to the words 'Initial size (MB)' enter the number 1536.
8. In the text box next to the words 'Maximum size (MB)' enter the number 3072.
9. Click on the Set button.
10. Press the OK button and allow your computer to reboot.

That should be all you need to do. If you can, please write down the previous numbers before you changed them and post them here. After you've rebooted follow steps 1-5 again and check to make sure that the new numbers you set are still there. If everything is good go ahead and give GW a try. Hopefully that takes care of you... If it continues to give you problems post here again and we'll try something else.

Beware · Feb 06, 2008, 08:46 PM // 20:46

The numbers I had before were 768, but my recommended was 1906, so I changed it to that, and now im changing to 1536.

Beware · Feb 06, 2008, 09:24 PM // 21:24

I tried it. Usually, when I'm playing GW, I use vent for communication. I was using vent and trying it out, it just happened again.

Out Of Memory
ImgMem.cpp(154)

Beware · Feb 06, 2008, 09:38 PM // 21:38

BTW, Narada, can I have you GW IGN so I can PM u instead of continuesly posting on the forums?

Narada · Feb 07, 2008, 01:47 AM // 01:47

(PM sent)

Please download memtestx86 and burn the iso file to disc (make sure to burn it as an iso image and not a normal data CD.) When that's done reboot with the disc in your CD tray and tell memtest to start scanning. It'll take a bit and the tests will go on infinitely until you tell it to stop, so just take a gander at how many full tests it has done every once and awhile. If it hasn't found any errors after a few completed tests go ahead and reboot and we'll figure something else out. If it finds errors/bad modules/etc. you can reboot and let us know, then we'll get started on figuring out which memory stick is bad.

Beware · Feb 07, 2008, 03:39 PM // 15:39

I don't know which file and how to run the test. Plz, can u give full instructions to how to do the test?

MetalMan · Feb 07, 2008, 05:02 PM // 17:02

I had this...

It turned out to be that the northfield chip was severely overheating. Maybe try checking the temperature of your system?

Narada · Feb 07, 2008, 11:46 PM // 23:46

If he has any integrated sensors on his motherboard Everest will likely pick them up. He might be able to check out his temperatures that way, but it wouldn't be very accurate unless he ALT-TAB'ed to it to check while GW is running. (I believe you would click on the Computer icon and then the Sensors icon when you have it running, but I haven't used it in awhile.)

I can't remember if you mentioned it or not, but did you say that this problem only started happening after you ran that last Windows Update, or did you install new graphics drivers too? It'd be nice if all you had to do was install the newest drivers for your video card and then have that solve the problem.

-edit-
Before doing any of the below, completely turn off your computer and unplug it. After 10 or so seconds plug it back in and give things a try.
/edit

Anyways, for running memtestx86, download this file and extract/unzip its contents, which should be an .iso file.

Next, assuming that you have burning software, you need to burn that iso to a blank CD. When burning be sure to choose the option that will probably say something like 'burn image to disc' or 'iso' as opposed to a data or music CD. Select the iso file and burn it, then when it's done you should keep the disc in your CD drive and reboot your computer. The memtestx86 diagnostics tool should boot and allow you to perform tests. Here's some more detailed instructions from on the burning process if you have any confusion:

(as quoted from x86-secret.com)

Code:

For Windows, unzip the package into a directory like C:\memtest. You will
      now see a file called memtest86+-1.xx.iso in this directory. You will
      need to burn this file to a CD with a CD recording program. Do note
      however that you should not make a regular data CD on which you for
      instance write your text documents and holiday photographs. Instead the
      iso file is a so called image of a CD, it is a direct copy of a CD. Your
      CD recording program will most likely have a feature called burn image or
      something to that effect which you should use to burn the CD. Do NOT under
      any circumstances select to create a bootable CD. The memtest ISO image is
      already bootable. You need NOT create a new CD, you need to burn a CD
      image. Usually you can simply double click the iso file in the Windows
      explorer which will start your CD burning application and prompt you to
      burn the CD.

Reading this should help with understanding the program's usage:

Code:

Using Memtest
  -------------

  - How long does memtest run? How do I stop it?

    Memtest runs indefinately unless you stop it. It does however repeat the
    same tests over and over again. Memtest86+ contains a number of different
    tests which each take different approaches in trying to expose any errors
    in your memory. In the top right of your screen you can see the progress of
    each test in the lower of the two progress bars. The topmost progress bar
    shows the progress of a pass, each pass consists of all the tests in the
    memtest suite.

    Thus all tests are executed in one pass, so does that mean that no errors
    will show after the first pass if that pass didn't reveal any errors? Well
    no, there are several reasons why errors might only show up after a number
    of passes. Firstly as of this writing, the latest version of memtest also
    includes a test which uses random test patterns, each pass these patterns
    will of course be different. Secondly some types of errors simply don't show
    up until the system has been running for a while or are very critical on a
    certain timing condition, are thermal in nature, or other such conditions.

    To conclude, one successful pass of memtest will give you a pretty good
    idea that your memory is ok, only in rare cases will there be errors
    showing after the first pass. To be sure though simply have the test run
    overnight or even for a couple of days depending on the level of importance
    of the system.

Let memtestx86 keep working overnight and check up on it the next morning to see if it found any errors, then reboot with the disc out of the CD drive and report back to us. If you have any questions I'll be hopping on GW right now for a few hours.

therangereminem · Feb 07, 2008, 11:55 PM // 23:55

i got this alot sence getting new computer with vista, question is do you have vista,

ifyou do upgrade your ddr that willsolveyou problem, on my old computer with xp i had 1 gig ddr, never had a issue,new computer i did 1 gig also had the issue alot after paying for about 3 or so hours,

issue is vista req alot of memory to run about 750mb so only havn the 200 about left over and running vent and guild wars + other thinsg it wont be enough, what you need is 1 gig for vista 1 gig for guildwars and 1 gig for everythign else i use 4 gig atm i stopped hainvg the issue wheni went to 2 gigs of ddr2

Beware · Feb 08, 2008, 08:05 PM // 20:05

I recently got 1GB of DDR 333 PC2700 RAM and I have 256MB DDR 333 PC2700 RAM from before. I only have 2 slots. Is there any other way other than memtest? How can I check what drivers I have and if I need to update them or not.

IGN: Beware I Am Here

Narada · Feb 08, 2008, 11:04 PM // 23:04

I personally have only used memtestx86 to check memory, but someone else here might know of other reliable programs. As for drivers, do you have an ATI or NVidia graphics card?

Beware · Feb 09, 2008, 12:52 AM // 00:52

I have a onboard graphicscard, Intel.

Maybe doing the /dxdiag might help solve the issue after u know my comp specs.